Export to Microsoft Excel Quick Action

About the Export to Microsoft Excel Quick Action

Parameters

Classic Action Designer: Export to Microsoft Excel Action

About the Export to Microsoft Excel Quick Action

You can use the Export to Microsoft Excel action to export all or some of the field values from a business object in the these file formats:

  • Microsoft Excel 2007 and later (.xlsx)
  • Microsoft Excel 2003 and earlier (.xls)
  • Comma Separated Values (.csv)
  • XML (.xml)

The output contains the rows from a query created within its action wizard. The list of columns exported is the same as shown in the list view by default, but you can override or expand them here. This action creates only one worksheet.

You cannot use the Export to Microsoft Excel action in a composite action.

Neurons for ITSM automatically applies sorting settings to any records that you export, including from the dashboard and the Saved Searches Overview page.

When you use the Export to Microsoft Excel action, the spreadsheet file is sorted with both the simple sort order and the multi-sort settings that you previously set in the list.

If you want to export the list data from user interface, export to browser. Neurons for ITSM saves the exported file to your local application. The export to browser option cannot be used in a composite action.

If you want to run this action in the background through a workflow or schedule, export to a remote host connection. Neurons for ITSM saves the exported file to the specified remote host. You can automate the Export to Microsoft Excel action by scheduling the workflow that can run this action. See Using Workflows.

You can open an XML spreadsheet in Microsoft Excel 2007 and later.

By default, this action limits processing to 50,000 records at one time. Neurons for ITSM on-premise customers can change this default value in the web.config file on the Neurons for ITSM application server. The value to change is <add key="MaximumRowsForExcelExport" value = "50000"/>.

Parameters

To access the parameters select the Action Block to display them in the Settings pane.

Action Block Settings

Block Label: A unique name for the block. This is useful to identify each action when you have more than one of the same action block added or cloned in the design area.

Click the Export Inputs button to open the Export Inputs workspace in the Graphical Action Designer.

  • Export Format: Use the dropdown menu to select your preferred output format:
    • Excel - 2007 and Above
    • Excel - lower version
    • Comma separated values
    • XML
  • Column Header: The name of the item whose value is given in the Fields to Export column or in the Value Expression column.
  • Fields to Export: The name of the field to export. Choose a value from the drop-down list.

    You can specify either a value in the Fields to Export column or a value in the Value Expression column, but not both.

  • Value Expression: An expression that describes the column header item to export. For more information on expressions, see About Expressions.

    This action does not support the FormatDate built-in function.

  • Adds fields to the export list.
  • Removes fields from the export list.
  • Ok: Saves your entries for Export Inputs.
  • Cancel: Exits the Export Inputs workspace without saving your entries.

Export To: The destination for the data export. You can specify to a browser or to an external connection, if one exists. Click the external connection icon to specify an external connection. You must create the external connection before you can select it. See Exporting Data for more information.

Saved Search: Runs a saved search against the values specified in the Fields to Export column or in the Value Expression column. To use this option, you must specify an external data connection.

Click Save to commit your settings.

Start Block Settings

These settings are accessed by selecting the Start Block, see Start Block Settings.

This action does not respect the Auto-save checkbox option in the Start Block settings. It does save changes directly to the database, but please ensure that the behaviour you expect still occurs.